Method and system for managing multiple applications in near field communication

ABSTRACT

Apparatus and method for managing connections of a plurality of devices by a Near Field Communication (NFC) Controller (NFCC) through NFC. The method includes setting identification information of an entity, the entity being requested from an NFC device for a connection with the NFC device; and setting a logical link between the NFC device and the entity based on the identification information.

PRIORITY

This application is Continuation of U.S. patent application Ser. No.13/055,045, which was filed in the U.S. Patent and Trademark Office onJan. 20, 2011, as a National Phase Entry of PCT InternationalApplication No. PCT/KR2009/003957, which was filed on Jul. 17, 2009, andclaims priority to Indian Patent Application No. 1760/CHE/2008, whichwas filed in the Indian Patent Office on Jul. 20, 2008, the entirecontent of each of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention, in general, relates to a field of managing datain short range wireless communication. More particularly, the presentinvention relates to a method and system for managing multipleapplications in Near Field Communication (NFC).

2. Description of the Related Art

Communication devices such as mobile phone, Personal Digital Assistance(PDA), Laptops are frequently used for communication, for example,communication over a telecommunication network and short rangecommunication. The communication over the telecommunication network canbe a wired network and/or a wireless network. An example of wirednetwork includes a Public Switched Telecommunication Network (PSTN).Examples of wireless network include Global System for Mobile (GSM),Code Division Multiple Access (CDMA), and the like. The short rangecommunication can be established when communication devices are in aclose proximity to each other. Examples of short range communicationnetwork include, but are not limited to Bluetooth, infraredcommunication, Near Field Communication, etc.

Near Field Communication (NFC) is a short-range high frequency wirelesscommunication technology. In NFC a communication link is establishedautomatically as soon as two NFC enabled communication devices areplaced close to each other. NFC enables exchange of data between devicesthat are within ˜10 centimeter distance. NFC compatible communicationdevices adheres to ISO 18092 standards. Further, NFC compatiblecommunication devices can operate in different operating modes, forexample, reader/writer mode, peer-to-peer mode, and card emulation mode.The different operating modes are based on ISO/IEC 18092-NFCIP-1 andISO/IEC 14443 contactless smart card standards. For the sake of clarityand for the purpose of this description, the NFC compatiblecommunication devices will be referred as communication devices.

In reader/writer mode, the communication device is capable of readingNFC forum mandated tag types. A tag in this mode is either active orpassive. However, the tag is activated for communication when a readercommunication device is at a close proximity to the tag. In CardEmulation mode, the communication device hosts a NFC tag that is used asa traditional contactless smart card. In the Peer to Peer mode ofoperation, a legacy NFC communication device works in a Half-Duplex modeof operation using protocols that enable Peer to Peer mode of operation.

Hence, the NFC communication devices operate in three different modes.The main parts of a NFC communication device operation include NFCController (NFCC), Device Host (DH), and removable entities. An exampleof DH includes a processor. The removable entities include secureelements (SE) and/or non-secure elements. The NFCC interfaces andinteracts with the DH and the removable entities directly throughphysical links. The interactions are managed by the protocols in theNFCC, DH and removable entities. Hence, the interaction among the NFCC,the DH and the removable entities results in transfer of applicationdata over the NFC wireless link. In NFC communication devices, multipleapplications can be deployed on DH and removable entities. Further theinteraction of the multiple applications with other applicationsentities within the same NFC communication device and also with otherNFC communication devices is managed by the NFCC.

SUMMARY OF THE INVENTION

The present invention has been made to address at least the aboveproblems and/or disadvantages and to provide at least the advantagesdescribed below.

Accordingly, an aspect of the present invention is to provide a methodand system to efficiently manage operations associated with multipleapplications in the NFCC.

In accordance with an aspect of the present invention, a method isprovided for managing connections of a plurality of devices by a NearField Communication (NFC) Controller (NFCC) through NFC. The methodincludes setting identification information of an entity, the entitybeing requested from an NFC device for a connection with the NFC device;and setting a logical link between the NFC device and the entity basedon the identification information.

In accordance with an aspect of the present invention, a Near FieldCommunication (NFC) Controller (NFCC) is provided for managingconnections of a plurality of devices through NFC. The NFCC includes aprocessor configured to set identification information of an entity, theentity being requested from an NFC device for a connection with the NFCdevice, and set a logical link between the NFC device and the entitybased on the identification information, and a memory configured tostore the identification information.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present invention will be more apparent from thefollowing detailed description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an exemplary environment, in accordance with oneembodiment of the present invention;

FIG. 2 illustrates a Near Field Communication Controller (NFCC), inaccordance with one embodiment of the present invention;

FIG. 3 illustrates representation of data stored in a memory inaccordance with one embodiment of the present invention;

FIG. 4 illustrates a method for handling operations associated with aplurality of applications in a Near Field Communication Controller(NFCC), in accordance with one embodiment of the present invention; and

FIG. 5 illustrates a flow diagram for handling operations associatedwith plurality of applications in a Near Field Communication Controller(NFCC), in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Various embodiments of the present invention will now be described indetail with reference to the accompanying drawings. In the followingdescription, specific details such as detailed configuration andcomponents are merely provided to assist the overall understanding ofthese embodiments of the present invention. Therefore, it should beapparent to those skilled in the art that various changes andmodifications of the embodiments described herein can be made withoutdeparting from the scope and spirit of the present invention. Inaddition, descriptions of well-known functions and constructions areomitted for clarity and conciseness.

In the accompanying figures, similar reference numerals may refer toidentical or functionally similar elements. These reference numerals areused in the detailed description to illustrate various embodiments andto explain various aspects and advantages of the present disclosure.

Persons skilled in the art will appreciate that elements in the figureis illustrated for simplicity and clarity and may have not been drawn toscale. For example, the dimensions of some of the elements in the figuremay be exaggerated relative to other elements to help to improveunderstanding of various embodiments of the present disclosure.

The terms used to describe various embodiments are exemplary. It shouldbe understood that these are provided to merely aid the understanding ofthe description, and that their use and definitions in no way limit thescope of the invention. Terms first, second, and the like are used todifferentiate between objects having the same terminology and are nowhere intended to represent a chronological order, as and where statedotherwise. A set is defined as a non-empty set including at least oneelement.

FIG. 1 illustrates an exemplary environment 100 in accordance with oneembodiment of the present invention. The environment 100 includes a NFCdevice 102. The NFC device 102 is shown to include a Near FieldCommunication Controller (NFCC) device 104, a Device Host (DH) 106, twosecure elements (SE1 and SE2) 108 and 110. The DH is associated withthree applications, for example an application 112 (DH-App1 112), anapplication 114 (DH-App2 114) and an application 116 (DH-App3 116). Thetwo secure elements are also associated with one NFC applications each,for example an application 118 (SE1-App1) and an application 120(SE1-App2). However, only two secure elements and one DH are shown inthe environment 100, it will be apparent to the person ordinarilyskilled in the art that the environment 100 includes more number ofsecure elements and DH. Further, the number of applications associatedwith the DH and secure elements may also vary.

For NFC communication, the applications in the DH 106 and the secureelements 108 and 110, interact and communicate initially with the NFCC104 in the NFC device 102. For example, the DH 106 is connected to theNFCC 104 using a physical link 122. In an embodiment, the applicationsresiding in the DH 106 and the SE s (108 and 110) interact with NFCCusing one or more NFC Controller Interface, For example NFC Controllerinterface 124 and 126. The NFC communication can be internalcommunication and/or external communication. The internal communicationincludes interaction between one or more elements within the same NFCdevice. For example in the NFC device 102, the internal communication iswhen an application in the DH 106 communicates with an application inthe secure element 108 and/or the secure element 110 and/or vice versa.

The external communication is when applications residing in an elementin one NFC device interact with an application residing in an element inanother NFC device. For example in the environment 100, the externaloperation is when an application in the DH 106 and/or secure element 108and/or 110 interacts with an application residing in an element in aremote NFC device. The applications residing in the DH 106 and SecureElement (SE) 108 and 110 communicates with applications residing inother NFC devices using the NFCC 104, the NFCC 104 in turns uses NFC airinterface for communication. This results in application data transferover the NFC wireless link.

In an embodiment, the data transfer associated with a plurality ofapplications is managed by the protocols in the NFCC 104. The pluralityof applications associated with the DH 106 and secure elements 108 and110 are managed by the NFCC 104 by creating logical links. In anembodiment, a logical link is used to identify a communication pathbetween the NFCC 104 and the applications residing in the DH, SE or witha remote NFC device. The interaction between the NFCC 104 and the DH 106and the interaction between the NFCC 104 and the SE s 108 and 110 occursinside an NFC device 102. Hence, the NFCC 104 manages operationsassociated with a plurality of applications residing in the DH 106, theSE 108 and the SE 110 by maintaining and storing a plurality ofinformation associated with each application in the NFCC 104.

In an embodiment, information associated with the plurality ofapplications are Source Host Identity (ID), Destination Host ID and alink ID associated with each of the applications associated with DH andSE, for example the DH 106 and the SE s 108 and 110. The Source Host Idis the identity of a source element in which an application that hasrequested communication is residing. The Destination Host ID is anidentity of a destination element with which the application hasrequested to communicate. The logical link identity (ID) is a uniqueconnection identity that is created when a link between an applicationand the NFC controller is established.

For example, when DH-App1 interacts with SE1-App1, the Source Host ID isthe ID of the DH 104, the destination Host ID is the ID of the SE 108and link ID is a unique connection identity that will be generated whena link will be established between the DH 104 and the SE 108. Similarly,information associated with a plurality of application interactions isstored in the NFCC 104. Thereby, the NFCC 104 manages the plurality ofoperations associated with application in the NFC device.

FIG. 2 illustrates a Near Field Communication Controller (NFCC) 104 inaccordance with one embodiment of the present invention. To explain theFIG. 2, references will be made to FIG. 1. However, it will be apparentto a person ordinarily skilled in the art that the present invention canbe explained with the help of any other suitable embodiment of thepresent invention. The NFCC 104 includes a memory 202 and a processor204. The memory 202 is capable of storing a source host identity (ID), adestination host ID and a link ID associated with each application fromone or more applications.

In the environment 100, the memory 202 is capable of storing informationassociated with the applications residing in the DH 106, the SE 108 andthe SE 110, when the applications interact with each other or withapplications residing at remote device. For example the memory 202stores information associated with applications DH-App1, DH-App2,DH-App3, SE-App1 and SE-App2, when the applications interact with eachother or applications residing at remote device. For example, whenDH-App1 interacts with SE1-App1, the source host ID, the destinationhost ID and the link ID associated with the communication is stored inthe memory 202.

In an embodiment, a source Host ID, a destination host ID and a link ID,associated with one or more applications, is stored collectively andsimultaneously when the one or more applications interacts with otherapplications. Further, the processor 204 manages operations associatedwith the one or more applications simultaneously based on the sourcehost ID, the destination host ID and the link ID stored in the NFCC.

FIG. 3 illustrates a representation of data stored in a memory inaccordance with one embodiment of the present invention. To explain theFIG. 3, references will be made to FIG. 1 and FIG. 2. However, it willbe apparent to a person ordinarily skilled in the art that the presentinvention can be explained with the help of any other suitableembodiment of the present invention.

The environment 300 shows a memory 202 associated with the NFCC 104. Inan embodiment, the memory 202 stores information associated with one ormore applications when the one or more applications communicate withother applications. In an embodiment, the memory 202 stores a sourcehost ID, a destination host ID and a link ID associated with each of theone or more application, when the one or more application is interactingwith other applications. In another embodiment, the memory 202 storesany of a source Host ID, a destination host ID, a link ID, anapplication ID, a protocol ID, or a registration ID associated with eachof the one or more applications.

Hence, when an application, for example a DH application 112 (theDH-App1) communicates with other applications, for example the SE-App1,a source host ID, a destination host ID, a link ID, an application ID ora protocol ID associated with the application DH-App1 is stored in thememory 202. For example, the source host ID is the identity of the DH106, the destination host ID is the identity of the SE 108, the link IDwill be a logical link ID that will be generated when a link is createdwith the NFCC 104.

In an embodiment, the application ID identifies an application with aunique identifying mechanism. The application ID is a predefinedidentifier set by NFC standards or it can be defined as a new identifierfor NFC applications. The Protocol ID identifies a protocol with aunique identifying mechanism. The protocol ID is a predefined identifierset by NFC standards or it can be defined as a new identifier for NFCprotocols that are operating in the NFCC or using the NFC ControllerInterface. The registration ID is required to securely identify aremovable element such as a Secure Element or any other removableelement. This ID is created when the secure element or a non-secureelement is inserted in a NFC device for the first time afterauthentication a procedure occurs.

In an embodiment, the information associated with the one or moreapplications that are communicating is stored in a tabular format 302 inthe memory 202. The tabular format 302 shows five different fields, forexample a Source Host ID field, a Destination Host ID field, a Link IDfield, an Application ID field and a Protocol ID field. Though sixfields are shown in FIG. 3, it no where limits the scope of theinvention to six fields. Hence, a person ordinary skilled in the art canhave more or less number of fields in the memory 202. Further, themethod can also be performed with more or less number of fields.

FIG. 4 illustrates a method for handling operations associated withplurality of applications in a Near Field Communication Controller(NFCC), in accordance with one embodiment of the present invention. Toexplain the method 400, references will be made to FIG. 1. However, itwill be apparent to a person ordinarily skilled in the art that thepresent invention can be explained with the help of any other suitableembodiment of the present invention. The method 400 can also includemore number of steps as depicted in FIG. 4. Further, the order of thesteps may also vary. In an embodiment, the method is performed by theNFCC.

At step 402 the method 400 is initiated. At step 404, the method 400stores a source host identity (ID), a destination host ID and a link IDassociated with each application from the one or more applications. Inan embodiment, the source host ID, the destination host ID and the linkID is stored in the memory 202 when an application residing in anelement interacts with other applications. For example, when the DH-App1communicates with the SE-App1 and DH-App2 communicates with the SE-App2,the information associated with the communication is stored in thememory 202 of the NFCC 104. In an embodiment, the information associatedwith the communication is a source host ID, a destination host ID and alink ID.

In an embodiment, the source host ID is the ID of the entity where aninitiating application resides. The initiating application is anapplication that initiates a communication. Hence, identity of the DH106 is the source host ID when the DH-App1 initiates communication withother applications. In an embodiment, the destination host ID is the IDof the entity where a requested application resides. The requestedapplication is an application which is requested by the initiatingapplication for communication. For example, when the DH-App1communicates with the SE-App1 then the destination host ID is the ID ofthe Secure Element 108.

In an embodiment, the link ID is a logical link ID that is generatedwhen the communication between the entities within the same electronicdevice is established. For example, when the DH-App1 communicates withthe SE-App1 then the link ID is the logical link ID that is generated atrun time. In another embodiment, when an application, for example theDH-App1 communicates with an application residing in other NFC devicethen the logical link ID is a predefined ID. Hence, the NFCC stores thepredefined ID as the link ID when the application in the source hostinteracts with a destination host over a NFC air interface.

At step 406, the method 400 manages the one or more applicationssimultaneously based on the source host ID, the destination host ID andthe link ID stored in the NFCC. In an embodiment, the method managescommunication associated with the one or more applications in the NFCdevice 102 simultaneously. In an embodiment, the one or moreapplications are stored in a Device Host (DH). In an embodiment, the oneor more applications are stored in a removable elements associated withthe NFC device. In an embodiment, the one or more applications arestored in DH and/or removable elements or both. The removable elementsare secure element and/or a non-secure element.

In an embodiment, the method 400 also stores a registration ID alongwith the source host ID, destination host ID and link ID. In anembodiment, the registration ID is stored when an application, that isinitiating the communication, is residing in a removable element. Theremovable element is an entity that can be connected and disconnectedfrom an NFC device. In an embodiment, an application in a removableelement registers itself with the NFC device when the removable elementis connected with the NFC device.

Thereafter, a registration ID is generated when the device issuccessfully connected and identified by the NFCC. Hence, the method 400then manages the one or more applications based on the registration IDalong with the source host ID, destination host ID and link ID. In anembodiment, each of the one or more applications interacts with NFCCusing a predefined dedicated link when the communication is within theNFC device. In this embodiment, the one or more applications areresiding in one or more Secure Elements (SE) associated with the NFCdevice. The predefined link is used to transport the command, events ordata of one or more applications to the Device Host. In an embodiment,the predefined dedicated link is created when the NFCC is initialized.

The predefined dedicated link, for example a Routing_SE_Link or aTunnel_SE_Link, can be pre-allocated in the NFCC 104 for the purpose ofrouting data from the one or more SE (108 and 110) to the DH 106. Forexample, a link ID OxFF can be pre-allocated in the NFCC 104 to handlerouting of traffic from one or more SE (108 and 110) to the DH 106. Thislink can be pre-established between the NFCC 104 and DH 106 while theNFCC is initialized.

In an embodiment, the applications that are residing in one or more SEcan communicate to the NFCC and the peer device over NFC interface only.Hence, there can be message exchanges required between the SE and theDH. Therefore, the NFCC creates the dedicated link, for example theRouting_SE_Link or the Tunnel_SE_Link, that can be used to carry dataframes or other information frame from one or more SE to the DH. In anembodiment, the frames carry necessary information like Application ID,SE_ID that is required by the DH to act on the data carried in theframe.

In an embodiment, the method 400 stores a protocol ID along with thesource host ID, destination host ID and link ID. The protocol ID is theID associated with a protocol that is used by an application, forexample DH-App1, to communicate with other application, for example theSE-App1. In this embodiment, the method manages the one or moreapplications simultaneously based on the source host ID, the destinationhost ID, the link ID and the protocol ID.

In an embodiment, the method 400 stores an application ID along with thesource host ID, destination host ID and link ID. The application ID isthe ID that associated with an application when the NFCC identifies andinitializes the application, for example DH-App1. In this embodiment,the method manages the one or more applications simultaneously based onthe source host ID, the destination host ID, the link ID and theapplication ID.

In an embodiment, the method stores at least one of a source hostidentity (ID), a destination host ID, a link ID, an application ID, aregistration ID or a protocol ID associated with each application fromone or more applications. For example, the method 400 can store onlyapplication ID and protocol ID associated with one or more applications.In another example, the method 400 can store only a link ID and sourceID associated with one or more applications. Thereafter, the methodmanages the one or more applications simultaneously based on at leastone of a source host ID, a destination host ID, a link ID, anapplication ID, a registration ID or a protocol ID stored in the NFCC.

In an embodiment, the method manages one or more applications in the NFCdevice when the data associated with the one or more applications aresent to an applications residing in an elements in the same NFC deviceand/or to an application residing in a second NFC device. In anotherembodiment, the method manages one or more applications in the NFCdevice when the data associated with the one or more applications arebeing received from an applications residing in an elements in the sameNFC device and/or to an application residing in a second NFC device. Atstep 408, the method 400 is terminated.

FIG. 5 illustrates a flow diagram 500 for handling operations associatedwith plurality of applications in a Near Field Communication Controller(NFCC), in accordance with one embodiment of the present invention. Toexplain the flow diagram 500, references will be made to FIG. 1 and FIG.2. However, it will be apparent to a person ordinarily skilled in theart that the present invention can be explained with the help of anyother suitable embodiment of the present invention. The flow diagram 500can also include more or less number of steps as depicted in FIG. 5.Further, the order of the steps may also vary. In an embodiment, themethod is performed by the communication device.

At step 502, an application residing at Device Host (DH), for examplethe DH 106, request the NFC Controller (NFCC) 104 to establish acommunication session with other application, for example SE-App1.Hence, initiation of a logical link setup happens at step 502. At step504, the NFCC creates a logical connection and updates one or morefields in the memory 202 of the NFCC 104 with information associatedwith a logical connection. Hence, information associated a source hostID, a destination host ID and a link ID is stored in the memory 202 ofthe NFCC 104. For example, ID of the DH 106 is stored as a source ID andID of the SE 108 is stored as the destination ID when the DH-App1communicates with the SE-App1.

In an embodiment, an ID associated with a created logical link betweenthe DH-App1 and SE-App1 is also stored in the NFCC 104. In an example,the ID of the DH 106 is SH_ID1, the ID of the SE 110 is DEST_ID1 and thelogical link ID is a link_ID1. At step 506, a connection ID is reservedfor the connection associated with the application, for example theconnection ID is reserved for SH_ID1, DEST_ID1 and link_ID1. At step508, a logical connection event is created. At step 510, SE applicationsare registered with the NFC device. In an embodiment, the SEapplications are registered when a removable device is attached to theNFC device. At step 512, the DH 106 sends an identification command tothe secure elements for identifying the secure elements. In anembodiment, the identification command is sent using a functionSend_Identification_Command (CMD) as shown in FIG. 5.

At step 514, the secure element responds to the DH 106 with the SecureElement card identity. For example, the secure element sends a responseusing a function SE_Resp (Card_ID). At step 516, the secure element getsregistered. Further, a registration ID is generated in the DH 106. Forexample registration ID is Reg_ID1.

At step 518, the NFC Controller Interface (NCI) registers the secureelement SE1. In an embodiment, the NCI registers the secure elementusing function NCI_Host_Register SE1(REG_ID1). At step 520, a logicallink setup is initiated when an application residing in the secureelement (SE1) communicates with other applications. At step 522, alogical connection is created. In an embodiment, the logical connectionis created using the function Create Logical Connection (SH_ID2,DEST_ID2, link_ID2)). At step 524, a connection ID is reserved for thelogical connection associated with SH_ID2, DEST_ID2 and link_ID2. Atstep 526, a logical connection event is created for the applicationresiding at the SE1.

In an embodiment, the source host ID, the destination host ID and thelink ID associated with one or more applications in the NFC device arestored in the NFCC 104. This is done when the one or more applicationsinteract with other applications residing in the same NFC device or withan application residing in other NFC device. Thereafter, the operationsassociated with the one or more applications are managed based on theinformation stored in the NFCC. In an embodiment, an application ID, aprotocol ID or a registration ID is also stored in the NFCC.

Various embodiments of the present invention described above provide thefollowing advantages. The present invention provides a method formanaging operations associated with multiple applications in a NearField Communication (NFC) device. The method increases the efficiency ofthe NFC device as the information associated with a plurality ofapplications that are communicating with other applications are storedin the NFC Controller (NFCC). Hence, the NFCC can easily manage multipleapplications simultaneously.

The method enables the NFC device to perform lesser operations formanaging multiple applications. This increases performance of the NFCdevice and also reduces power consumption considering NFC operations arepower critical. The usage of Registration ID enhances the securityfeatures. Further, the discovery operations are also eased out by theusage of Protocol ID.

While the present invention has been particularly shown and describedwith reference to certain embodiments thereof, it will be understood bythose of ordinary skill in the art that various changes in form anddetails may be made therein without departing from the spirit and scopeof the present invention as defined by the following claims and theirequivalents.

What is claimed is:
 1. A method for managing, by a Near FieldCommunication Controller (NFCC), connections between a plurality ofentities through Near Field Communication (NFC), the method comprising:receiving a request, from a Device Host (DH), for information onentities connected with the NFCC; allocating identification informationcorresponding to each of the entities connected with the NFCC;transmitting at least portion of the identification information to theDH; receiving a request for connecting with at least one entity from theDH; setting at least one logical connection between the DH and the atleast one entity; and transmitting logical connection information on theat least one logical connection to the DH, wherein, when a connectionbetween a removable entity and the NFCC is detected by the NFCC,registration ID is allocated, by the NFCC, to the removable entityconnected to the NFCC.
 2. The method of claim 1, wherein theidentification information includes a source host IDentifier (ID) ofeach of the at least one entity, a destination host ID of each of the atleast one entity, a link ID of each of the at least one logicalconnection between the DH and the at least one entity, or theregistration ID.
 3. The method of claim 2, wherein setting the at leastone logical connection between the DH and the at least one entitycomprises: assigning the link ID to each of the at least one logicalconnection between the DH and the at least one entity.
 4. The method ofclaim 2, further comprising setting, by the DH, a link between the DHand the NFCC.
 5. The method of claim 4, wherein the link ID is set foridentifying the link between the DH and the NFCC, and is valid while thelink is maintained.
 6. The method of claim 5, wherein, when the linkbetween the DH and the NFCC is terminated, the link ID is used toidentify another link between another DH and the NFCC.
 7. The method ofclaim 4, wherein receiving the request for connecting with the at leastone entity from the DH comprises: receiving a request for initiating acommunication session for the at least one logical connection from theDH.
 8. The method of claim 1, wherein receiving the request for theinformation on the entities connected with the NFCC comprises: receivinga discovery command for discovering the entities connected with the NFCCfrom the DH.
 9. The method of claim 8, wherein transmitting the at leastportion of the identification information to the DH comprisestransmitting a discovery response corresponding to the discovery commandto the DH, and wherein the discovery response includes informationindicating current statuses of the entities connected with the NFCC,protocols supported by the entities connected with the NFCC, and anumber of the entities connected with the NFCC.
 10. The method of claim8, wherein a source host IDentifier (ID) is an identifier correspondingto each of the entities connected with the NFCC.
 11. A Near FieldCommunication Controller (NFCC) for managing connections between aplurality of devices through Near Field Communication (NFC), the NFCCcomprising: an NFC controller interface configured to receive a request,from a Device Host (DH), for information on entities connected with theNFCC; a processor configured to: allocate identification information toeach of the entities connected with the NFCC, control the NFC controllerinterface to transmit at least portion of the identification informationto the DH, control the NFC controller interface to receive, from the DH,a request for connecting with at least one entity, set at least onelogical connection between the DH and the at least one entity, andcontrol the NFC controller interface to transmit, to the DH, logicalconnection information on the at least one logical connection; and amemory configured to store the identification information correspondingto each of the entities connected with the NFCC, wherein the processoris further configured to, when a connection between a removable entityand the NFCC is detected by the NFCC, allocate a registration ID to theremovable entity connected to the NFCC.
 12. The NFCC of claim 11,wherein the identification information includes a source host IDentifier(ID) of each of the at least one entity, a destination host ID of eachof the at least one entity, a link ID of each of the at least onelogical connection between the DH and the at least one entity, or theregistration ID.
 13. The NFCC of claim 12, wherein the processor isfurther configured to assign the link ID to each of the at least onelogical connection between the DH and the at least one entity.
 14. TheNFCC of claim 12, wherein the DH sets a link between the DH and theNFCC.
 15. The NFCC of claim 14, wherein the link ID is set foridentifying the link between the DH and the NFCC, and is valid while thelink is maintained.
 16. The NFCC of claim 15, wherein, when the linkbetween the DH and the NFCC is terminated, the link ID is used toidentify another link between another DH and the NFCC.
 17. The NFCC ofclaim 14, wherein the processor is further configured to receive arequest for initiating a communication session for the at least onelogical connection from the DH through the NFC controller interface. 18.The NFCC of claim 11, wherein the processor is further configured toreceive a discovery command for discovering the entities connected withthe NFCC from the DH through the NFC controller interface.
 19. The NFCCof claim 18, wherein the processor is further configured to control theNFC controller interface to transmit a discovery response correspondingto the discovery command to the DH, and wherein the discovery responseincludes information indicating current statuses of the entitiesconnected with the NFCC, protocols supported by the entities connectedwith the NFCC, and a number of the entities connected with the NFCC. 20.The NFCC of claim 18, wherein a source host IDentifier (ID) is anidentifier corresponding to each of the entities connected with theNFCC.